TML-2597: SQL ORM many-to-many — project spec + plan#673
Open
Conversation
Shape the end-to-end many-to-many project: spec + 4-slice plan (0 contract+resolver foundation, gating parallel read/filter/write). Promoted from TML-2597 to a dedicated Linear Project; slices TML-2784..2787. No code changes — planning artifacts only. Signed-off-by: Alexey Orlenko's AI Agent <robot@aqrln.net>
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Jun 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Shaping artifacts for the SQL ORM: Many-to-Many End to End project. No code changes —
projects/sql-orm-many-to-many/only (spec, plan, README, trace).What this adds
spec.md— system-level intent: restore the relation-shaped ORM API (include / filter / nested write) over M:N, so users stop hand-wiring explicit junction models and the Pothos plugin stops rejecting M:N at build.plan.md— 4 slices: slice 0 (contract + resolver foundation) gates a parallel fan-out of read / filter / write.Key decisions captured
cardinality: N:Mand the undeclaredthroughkey. Slice 0 closes that; it is a real gap, not prep.throughdescriptor on the single shared resolver, consumed three ways (not junction-as-nested-include, which does not generalise to filter/write).connect/disconnect/create); nestedupdate/upsert/delete/setare out of scope → TML-2781.Linear
Promoted from TML-2597 to a dedicated Linear Project (SQL ORM: Many-to-Many End to End). Slices: TML-2784 (0) / TML-2785 (1) / TML-2786 (2) / TML-2787 (3).
Scope statement
Planning artifacts only. No package code, no fixtures, no behavior change. Refs: TML-2597.